chore: Fix configuration of EhCache 3 #3118
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes the upgrade of EhCache (see #3098). There is one cache (
invalidatedJwtTokens
) that persists data to be stale over restarts. The issue here is about the new implementation. EhCache creates a random access file and its channel. Then it creates off-heap caches (by linking data into memory), see:org.ehcache.shadow.org.terracotta.offheapstore.disk.paging.MappedPageSource:
In other OS than z/OS is possible to create multiple buffers at the same time (<0;1024), <1024;2048), etc.), but z/OS limits somehow this feature. It seems there are possible to allocate multiple buffers as well but with a limitation (blocks cannot be near each other, but with a non-specified gap).
The solution is to create just one buffer and avoid parallel access to this file. It is done by setting disk segments to 1.
Log:
Linked to # (issue)
Part of the # (epic)
Type of change
Please delete options that are not relevant.
Checklist:
For more details about how should the code look like read the Contributing guideline